Summary

This PR addresses issue reports around:

• Invalid AI type: trae / Invalid AI type: droid (e.g. uipro init --ai trae returns "Invalid AI type: trae" #195, uipro init --ai droid` returns "Invalid AI type: droid" #172)
• Missing frontmatter in generated RooCode/Kiro SKILL.md (e.g. The SKILL.md generated with the "uipro init --ai roocode" command does not have frontmatter #212)

What changed

1. Improved invalid AI type error guidance

   • Added a shared printInvalidAITypeError() helper in cli/src/index.ts.
   • Updated init, update, and uninstall command validation paths to use it.
   • Error output now includes explicit upgrade guidance:
     • uipro --version
     • npm install -g uipro-cli@latest
     • retry command

2. Added CLI troubleshooting docs

   • Added troubleshooting section in cli/README.md for:
     • Invalid AI type: trae/droid
     • RooCode/Kiro frontmatter regeneration steps
   • Added matching troubleshooting section in root README.md for quick visibility.

3. Added platform config verification script

   • New script: cli/scripts/verify-platform-configs.mjs
   • Verifies:
     • trae and droid are present in cli/src/types/index.ts
     • roocode and kiro platform configs contain non-empty frontmatter (name, description)
   • Added npm script:
     • verify:platform-configs in cli/package.json

Testing

• npm --prefix cli run verify:platform-configs
• npm --prefix cli run build
• node cli/dist/index.js init --ai not-real

Related Issues

• The SKILL.md generated with the "uipro init --ai roocode" command does not have frontmatter #212
• uipro init --ai trae returns "Invalid AI type: trae" #195
• uipro init --ai droid` returns "Invalid AI type: droid" #172